Update EVM Accounts text #675
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
gregsantos
suggested changes
Mar 25, 2024
|
|
||
| For more information on Cadence Owned Accounts, see the [Flow EVM Support FLIP](https://github.com/onflow/flips/pull/225/files) | ||
| [EOAs and Contract](https://ethereum.org/developers/docs/accounts) accounts function the same as on other EVM networks. EVM developers can use EVM on Flow without having to use COAs. However, in order to unlock all the features of Cadence, developers may choose to utilize Cadence Owned Accounts. |
There was a problem hiding this comment.
Suggested change
| [EOAs and Contract](https://ethereum.org/developers/docs/accounts) accounts function the same as on other EVM networks. EVM developers can use EVM on Flow without having to use COAs. However, in order to unlock all the features of Cadence, developers may choose to utilize Cadence Owned Accounts. | |
| [EOAs and Contract](https://ethereum.org/developers/docs/accounts) accounts function the same as on other EVM networks. EVM developers can use EVM on Flow without having to use COAs. However, in order to unlock all the features of Cadence, developers may choose to take advantage of Cadence Owned Accounts using a Flow compatible wallet. |
There was a problem hiding this comment.
maybe link out to Wallets page?
| @@ -16,17 +16,10 @@ There are three types of accounts used for EVM on Flow. | |||
|
|
|||
| 1. **Externally Owned Accounts (EOA)**: EOAs are controlled by private individuals using cryptographic keys and can initiate transactions directly. They are the primary account type for users to interact with the blockchain, holding and sending cryptocurrency or calling smart contract functions. | |||
| 2. **Contract Accounts**: These accounts hold smart contract code and are governed by this code's logic. Unlike EOAs, Contract Accounts do not initiate transactions on their own but can execute transactions in response to calls they receive from EOAs or other contracts. | |||
| 3. **Cadence Owned Accounts (COA)** | |||
| 3. **Cadence Owned Accounts (COA)**: Bridging Cadence and EVM environments, COAs operate similarly to EOAs but execute transactions directed from Cadence. Created from Cadence without a key, COAs are assigned a 20-byte EVM address. As a Resource type owned by a Flow account in the Cadence Virtual Machine, COAs can run EVM transactions, deploy Solidity contracts from Cadence, and perform other EVM interactions. This integration allows developers to utilize the full potential of Cadence within the EVM framework on Flow. | |||
There was a problem hiding this comment.
Suggested change
| 3. **Cadence Owned Accounts (COA)**: Bridging Cadence and EVM environments, COAs operate similarly to EOAs but execute transactions directed from Cadence. Created from Cadence without a key, COAs are assigned a 20-byte EVM address. As a Resource type owned by a Flow account in the Cadence Virtual Machine, COAs can run EVM transactions, deploy Solidity contracts from Cadence, and perform other EVM interactions. This integration allows developers to utilize the full potential of Cadence within the EVM framework on Flow. | |
| 3. **Cadence Owned Account (COA)**: COA is a natively supported EVM smart contract wallet type owned by a Flow account and controlled by a Cadence resource. COAs provide powerful primitives which allow bridging and control of assets, including ERC721, ERC-20, and $FLOW native tokens, and ensuring seamless composability across Cadence and EVM environments. Unlike EVM Contract Accounts, COAs can initiate transactions on their own without needing an external EOA transaction to trigger them. | |
| **Key Features:** | |
| - COAs are exclusively created via Cadence, assigned unique 20-byte EVM addresses based on their UUID. | |
| - COAs can initiate and execute EVM transactions, deploy Solidity contracts from Cadence, and perform other EVM interactions, with their associated EVM address acting as `tx.origin`, and without need of an EOA trigger | |
| - They support native cross-VM bridging capabilities for a variety of tokens, detailed in the [Flow VM Bridge improvement proposal](https://github.com/onflow/flips/pull/233). | |
| - COAs provide dual interfaces for interaction within Flow EVM and Cadence environments. Additional details can be found in the [EVM Support FLIP](https://github.com/onflow/flips/blob/d01024385bf72e8d566f2502c343780603624210/protocol/20231116-evm-support.md#cadence-owned-account-coa) |
| @@ -16,17 +16,10 @@ There are three types of accounts used for EVM on Flow. | |||
|
|
|||
| 1. **Externally Owned Accounts (EOA)**: EOAs are controlled by private individuals using cryptographic keys and can initiate transactions directly. They are the primary account type for users to interact with the blockchain, holding and sending cryptocurrency or calling smart contract functions. | |||
There was a problem hiding this comment.
Suggested change
| 1. **Externally Owned Accounts (EOA)**: EOAs are controlled by private individuals using cryptographic keys and can initiate transactions directly. They are the primary account type for users to interact with the blockchain, holding and sending cryptocurrency or calling smart contract functions. | |
| 1. **Externally Owned Account (EOA)**: An Externally Owned Account (EOA) is a user-controlled account type that operates through cryptographic keys. These accounts are fundamental for user interactions with the blockchain, as they are capable of directly initiating transactions. EOAs serve as the primary gateway for users, allowing them to manage, send, and receive cryptocurrencies, as well as interact with smart contract functionalities. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.